Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use official Flake8 VS Code extension #203

Merged
merged 1 commit into from
Jan 28, 2024
Merged

Use official Flake8 VS Code extension #203

merged 1 commit into from
Jan 28, 2024

Conversation

caleb531
Copy link
Owner

@eliotwrobson Just a small quality-of-life improvement, but with a small caveat, and so want your feedback.

This commit switches the third-party cornflakes-linter VS Code extension
to the official Flake8 extension by Microsoft. I'm hoping this should fix an issue I've encountered with the former extension where files
within the virtualenv or within Python stdlib were linted when they
should have been ignored. I haven't tested that the new extension fixes this, but given that it's first-party, I'm optimistic that it's less buggy.

The catch with this change is that anyone who has installed the official Flake8 extension should uninstall cornflakes-linter (or disable it for the workspace) lest they see duplicate errors in the Problems panel (or otherwise experience other unforeseen conflicts between the extensions).

This commit switches the third-party cornflakes-linter VS Code extension
to the official / first-parrt Flake8 extension by Microsoft. This should
fix some issues I've encountered with the former extension where files
within the virtualenv or within Python stdlib were linted when they
should have been ignored.
@coveralls
Copy link

Coverage Status

coverage: 99.64%. remained the same
when pulling ebe48dc on flake8-official
into 13e5c1b on develop.

Copy link
Collaborator

@eliotwrobson eliotwrobson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your concern makes sense, but at the end of the day, I don't think anyone is going to freak out about the recommended extension changing (since they can confirm when it's installed).

@caleb531
Copy link
Owner Author

@eliotwrobson That's a good point. Especially since the recommendations are just that—they're not required or forced on VS Code users, and can be easily dismissed. With that, I think I'm going to proceed to merge this—thank you for your input!

@caleb531 caleb531 merged commit 5a36080 into develop Jan 28, 2024
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants